Power Tools 1993 October

home *** CD-ROM | disk | FTP | other *** search

/ Power Tools 1993 October - Disc 2 / Power Tools (Disc 2)(October 1993)(HP).iso / hotlines / network / tiostgy / script.txt < prev next >

Wrap

Text File | 1993-02-19 | 43KB | 1,074 lines

COMPANY CONFIDENTIAL HP Terminal Connect December 1991 WHITE PAPER V 2.0 Table of Content I. Executive Summary II. HP Terminal Connect Strategy Update II.1 Market Trends II.2 HP Terminal Connect Value Proposition II.3 HP Terminal Connect Segmentation II.4 HP Terminal Connect Objectives II.5 HP Terminal Connect Strategy II.6 HP Terminal Connect Vision III. A major step to achieve the DTC vision III.1 Multivendor DTC with consistent location-independent access III.2 Connectivity based on the DTC III.3 Telnet Services for the HP3000 Series 900 III.4 Enhanced Connectivity with the DTC, End 1991 III.5 DTC Features Analysis Short Description III.6 HP OpenView Network Management Applications Integration III.7 Competitive Host-Based Management III.8 Competitive Company-Wide Network Management III.9 Steps in HP3000 Series 900 terminal connect III.9 Steps in HP9000 Series 800 terminal connect III.10 HP's Multivendor advantage III.11 HP Results in the Terminal Server Market III.12 For more Information IV. A year in the life of MUXES for HP 9000 V. A year in the life of HP PADs VI. Conclusion .pa Note to the reader The following text contains slides that can be used for presentations to the sales force or customers. It is recommended that the slides are extracted in advance to facilitate reading. This White Paper has been updated with new information relative to theDTC, DTC Manager & MUXes products. ..pictureA:\custagda.gal,65381,49113,14,63,15, A typical (1 Hour) customer presentation could have the following agenda : HP Terminal Connect Strategy Agenda II.0 Agenda II.1 Market Trends (optional) II.2 HP Terminal Connect Value proposition II.3 HP Terminal Connect Segmentation II.4 HP Terminal connect Objectives (optional) II.5 HP Terminal Connect Strategy II.6 HP Terminal Connect Vision II.7 A major step to achieve the vision OR/AND II.8 A year in the life of MUXES for HP 9000 OR/AND II.9 A year in the life of HP PADs II.10 Conclusion Terminal I/O Strategy update Executive Summary Introduction The Purpose of this document is to provide : - An update on the strategic directions regarding HP terminal connectivity. - A status report on the current offering and a plan for the coming months. Evolution of end user connectivity requirements The requirements for end user connectivity has evolved dramatically during the past two years, as a direct result of market changes. - The HP 3000 was the only OLTP machine at HP - The HP 9000 was primarily a workstation, and HP-PA systems were targeted at the Engineering market as Compute Servers or PLC drivers on the manufacturing floor. - The HP 1000 was very successful on the manufacturing floor level, most often for data acquisition applications. To support this positioning HP had developed a family of MUXES for the HP 1000 and HP 9000 series systems for low numbers of connections. In transaction processing environments with the migration to MPE XL, HP moved away from MUX (ATP's) towards a LAN-based solution via a Datacommunication and Terminal Controller (DTC). The Market has evolved significantly since then: - Unix appeals to users for transaction processing applications. - OSI is delivering its promise for messaging systems, or more generally, file transfer, while TCP/IP still appears as a viable alternative for end user connectivity until OSI standards gain greater acceptance. - In the future, business needs will be served by open systems offering the following features: o Easy multivendor systems mix'n match o Inter-connection of sites world-wide o Simplicity - One coherent set of standards o Application portability o Protection of investment o Decrease of operating costs .pa This evolution trend in the systems market has affected the way HP's computers are being used: - HP 1000s are now more and more integrated with HP 9000s at manufacturing floor level. - HP 9000s have experienced a dramatic growth in the transaction processing business requiring adequate solutions. - HP 3000s require greater connectivity for both local and remote users - HP intersystem connectivity requirements have increased. - The demand for multivendor connectivity through standard protocols is growing rapidly. - Transparent wide-area communication requirements is a must to be achieved without increasing the complexity of network management. This evolution had a dramatic impact on the Terminal I/O strategy. HP views the TIO connectivity solution requirement to be broken out into three classes: MUXs, PADs, and terminal servers. The HP terminal connect strategy is based on a "best-in-class" approach, providing the most competitive and comprehensive solutions. The HP terminal connect strategy is based on three elements: - A competitive scalable Hardware Architecture of MUXs, PADs, and Terminal Servers. - Standards-based, multivendor, end-user connectivity solutions through: o Providing consistent location-independent user access. o Combining the benefits of standard and proprietary protocols. - Competitive scalable homogeneous device management based on HP OpenView. The combination of these three elements will offer HP competitive features to beat the competition and penetrate multivendor accounts. For more details about the strategic directions, and specific information about the current product offering and positioning, please read on. .pa II. HP Terminal Connect Strategy Update II.1 Market Trends ..picturea:\market.gal,65535,49151,1,79,24, With the increasing need for companies to communicate on a global scale, the need to exchange information is growing rapidly. Computer networks are increasingly being interconnected in response to business needs. Because of the tremendous growth in wide area connectivity devices, the requirement for transparent end-user connectivity over these backbones is growing. As networks grow, they tend to incorporate heterogeneous systems. Companies are looking for ways to provide end-users access to different systems in a multivendor environment. There is therefore a growth in equipment such as terminal servers which can provide a single access point to achieve transparent end-user connectivity. DEC pioneered this concept in the early 80's, and their proprietary protocol (LAT) holds a significant market share. However, the growth is today in the TCP/IP area. Growth is also expected in the SNA area and OSI as the Virtual Terminal Protocol standard gains acceptance. By migrating from asynchronous devices to LAN attached devices such as PCs, X-terminals and network printers, companies can facilitate end- user access to information. However, today there exists a large installed base of applications that are designed for asynchronous devices which have to be accessed by LAN attached devices with full transparency; new developments may use a different technology. As a consequence of the evolution of end-user devices, companies are also reviewing their wiring strategy to accommodate emerging technologies. Customer are adapting their wiring strategy to new technologies such as PC LANs or Multimedia applications ; therefore expect asynchronous devices to coexist and use these new wiring systems. In conclusion: There is still a growing demand for standards-based, cost-competitive, location-independent, multivendor connectivity. The successful companies are those who recognise these trends and help customers progress while protecting their investment in today's technology. .pa II.2 HP terminal Connect Value Proposition ..picturea:\value.gal,65535,49151,1,79,24, Companies want to be able to focus on meeting their business requirements. They will choose computer equipment, only if they believe it will satisfy their end-user requirements. In terms of end-user connectivity, customer service can be significantly improved in an environment where end-users can access the information they need when they may need it, with the minimal effort. This can only be achieved by focusing on key elements, such as performance, consistent location-independent access, reliability, and multivendor connectivity; while ensuring competitive cost of ownership. .pa II.3 HP terminal Connect Segmentation ..picturea:\SLIDE5.GAL,65535,49151,7,69,19, HP's strategy is built upon a recognition of four different segments that correspond to different end-user connectivity needs. 1) Single HP Standalone site : - Single small to mid-range system - Local connections only 2) Standalone HP remote site : - Standalone or clusters of end-user devices (terminals, printers) connected to modem or PADs. - PC networks. - Small to mid-range systems with terminals or PC's These sites can be connected to larger MIS HP sites, or MIS multivendor sites. 3) Multiple HP homogeneous : - Multiple mid-range to high-end systems - Homogeneous HP environment (MPE-MPE) (HPUX-HPUX) (MPE-HPUX-RTE) - Computers connected to LAN - Outbound/inbound communication with other sites equivalent in size or smaller. 4) Multiple HP multivendor : - Multiple mid-range to high end systems - Heterogeneous environment - Computers connected to LAN - Outbound/inbound communication with other sites equivalent in size or smaller. II.4 HP Terminal Connect objective ..pictureA:\slide9.gal,65535,49151,2,79,27, Customers want solutions which will meet today's business needs but will also be able to evolve seamlessly as requirements change. They want to be assured that solutions for a single-system environment will be able to grow as more computers are added whether they are supplied by HP or another vendor. In terms of terminal connectivity, the ideal solution would be consistent end-user access independent of systems and where they are located. HP Terminal connect objectives to meet customer expectations and leverage investment are to : - Provide competitive scalable offering for standalone and LAN-based multi-systems configurations. - Provide homogeneous solutions for all HP Computers. - Seamless integration and connectivity in multivendor environments. Providing all of these attributes will help HP become a key player in the end user connectivity business and more specifically in this still growing terminal server market. .pa II.5 HP Strategy ..picturea:\tiostrat.gal,65390,49151,2,79,27, HP's Strategy aims to provide "best-in-class" solutions to meet the business requirements of today and beyond. HP views the TIO connectivity solution requirement to be broken out as into three classes: MUXs, PADs, and terminal servers. The HP terminal connect strategy is based on a "best-in-class" approach, providing the most competitive and comprehensive solutions for each category. The HP terminal connect strategy is based on three elements: - A competitive scalable Hardware Architecture of MUXs, PADs, and Terminal Servers. - Standards-based, multivendor, end-user connectivity solutions through : o Providing consistent location-independent user access. o Combining the benefits of standard and proprietary protocols. - Competitive scalable homogeneous device management based on HP OpenView. The combination of these three elements will offer HP competitive features to help HP-only, and multivendor accounts. A Competitive Scalable Hardware architecture ..picturea:\slide06.gal,65535,49151,2,79,27, In terms of hardware, there are two determining factors for the best solutions to meet customer requirements: - The physical location of end-users relative to the computer room. - The number of connections to a specific system and the number of computers that need to be accessed by a given end-user. Actually, this perfectly matches the segmentation defined earlier. For small and medium standalone systems, HP's strategy is to offer system integrated solutions. The key attributes are: - simplicity - low cost - limited number of users/devices - small/concentrated physical environment HP's Strategy is to use MUXs or terminal servers that can be easily integrated into the computer package. The choice will depend on such things as the expected growth in port counts on this specific system, or the potential addition of other systems in the future. Depending on the number of users who require access to multiple systems, customers have the choice choosing either terminal servers or MUXs along with virtual terminal capabilities between systems. System access via PAD is also easily accomplished. For multi-system environments, with medium to large computers connected by LANs, where the end-user requires location-independent access, HP's strategy is to provide a modular terminal server that can accommodate a large number of users, and allow for the mixing of local and remote access cards. The key attributes are : - advanced functionality - multi-system, multivendor access - large number of users/device - large/dispersed physical environment When the equipment is centralised in the computer room, the modular terminal server can mix and match asynchronous access a cards and remote access cards. When connections are distributed throughout buildings, HP's strategy is to complement the modular terminal server with a smaller terminal server which can be distributed throughout buildings to serve smaller groups of users. This solution offers very high flexibility in terms of wiring, and it is homogeneous with the PC workgroup wiring concept. It also significantly decreases the cost of wiring should there be frequent connection additions and moves. This solution applies to both standalone and multiple systems environments. This segmentation is applicable to all HP systems. However the solution of choice in each segment is system- and application-dependent. .pa Best in class standard based multivendor end-user connectivity solutions ..picturea:\slide00.gal,65535,49151,2,79,27, HP's strategy aims to provide end-users with "best-in-class" end-user connectivity with: - Consistent location-independent, multivendor user access - The benefits of standard and proprietary protocols Please refer to each of the numbered items on the slide. To support this strategy, HP's vision is based on the following elements : 1. A multivendor terminal server capable of supporting OSI or de facto standard protocols such as OSI, AFCP, TCP/IP or LAT. HP is evlaluating the potential for implementing protocols such as LAT or OSI VTP. Plans for such offering may be disclosed in the future. 2. This server must offer consistent access to remote and local users. This will be achieved by integrating a PAD support functionality capable of interfacing with all protocols available in the server. Thereby, any user connected to remote private PAD (4) or public PAD will gain access to any system on the central site as if he was connected locally. 3. Finally, this protocol set must be available to other users using multivendor equipment such as terminals hooked up to TCP/IP terminal servers, PCs or Workstations running Telnet, provided they have the adequate terminal emulation. This will be achieved with the capability of converting protocols such as TCP/IP to AFCP, LAT or OSI. End-users will benefit from this implementation as they will have consistent access to systems which reside on networks interconnected with bridges or routers. Network managers will minimize the number of protocols on their backbone, making it easier to manage. Finally, these benefits will be obtained without giving up the performance and low overhead associated with proprietary protocols. 4. For remote sites consisting of terminals, printers and PCs, HP will continue to offer a competitive, scalable PAD offering. 5. When there is a system in the remote site (e.g branch office), it is often necessary to have interactive end-user traffic with the central site and also system to system communications. For these sites, HP's strategy is to combine both functionalities on the same integrated hardware. 6. When the environment requires terminal servers, HP's strategy is to combine local and remote capability in the server, by offering PAD emulation functionality on the server platform. .pa Competitive Scalable Homogeneous Device management based on HP OpenView ..picturea:\netstrat.gal,65535,49151,2,79,27, The third element of HP's Terminal Connect strategy focuses on the management of the Terminal Connect devices. To meet the needs of the segments identified earlier, HP's strategy is to offer two levels of network/device management. For standalone systems with or without remote access, HP's strategy is to offer Host-based Network Management. It aims at providing easy-to- use solutions in order to configure, manage and diagnose the devices as if they were integral part of the system. For multi-system sites, whether HP homogeneous or multivendor, where customers need to manage diverse equipment such as terminal servers, PADs, HUBs, Bridges, Routers, Switches, and other communication devices in addition to the systems themselves, HP's strategy is to rely on a specialized station capable of integrating all management elements under the control of one operator. This workstation runs Window based applications, integrated under the HP OpenView strategy. .pa III. A major step to achieve the vision III.1 Multivendor DTC for Transparent Local and Remote Access ..picturea:\int09.GAL,65535,49151,1,79,24, HP's Terminal server strategy is based on the DTC. The first step was to use the same hardware running different protocols. This resulted in the DTC/3000 and DTC/9000 versions of the DTC. The DTC/3000 was running the HP3000 optimized protocol, and the DTC/9000 was running Telnet/TCP/IP. The second step makes this hardware run multiple protocols on the same server. Now it's possible to access the HP 3000, and using TCP/IP/Telnet to access the HP9000 and other HP or non-HP systems which support the Telnet/TCP/IP protocol. These protocols are available for both local and remote via X.25 end-users to access local and remote via extended LANs systems. A protocol conversion capability is also provided via extra hardware if required for Telnet access to the HP3000 Series 900. At the same time, the DTC provides added services and functionalities. HP makes this possible on the current DTC hardware. DTC48's with a datecode < 3110 -corresponding to March-1991 - require a simple hardware upgrade ( memory extension ) to increase the DTC48 capacity. Note: the DTC16 does not require an upgrade. Now, any DTC is a multivendor communication server. Using the same product that your customer owns, HP provides added services & functionalities with the recent HP OpenView DTC Manager release 10.5 which has been available since June 1991. .PA III.2 CONNECTIVITY BASED ON THE DTC ..picturea:\int10.GAL,65535,49151,2,78,23, The DTC, originally developed as a terminal server for HP systems (DTC/3000 and DTC/9000), has evolved into a true multivendor communication server implementing both the HP3000 optimized protocol named "AFCP" and industry-standard Telnet/TCP/IP protocol. The DTC runs multiple protocols on the same server to provide the following new capabilities: 1) Access for local DTC end-users to HP9000 & Multivendor systems -in addition to HP3000 Series 900 systems- by using standard protocol Telnet/TCP/IP. This is true whether the systems are local or remote via Bridges, or extended LANs. 2) Access for remote end-users (connected to public or private PAD's) to these HP 9000 & Multivendor systems in addition to HP3000 Series 900 systems. 3) Access to remote -via extended LANs- HP3000 Series 900 systems by using a protocol conversion (From Telnet to the HP3000 protocol) done at the remote site. This is possible via additional hardware (see next page). .PA III.3 TELNET SERVICES FOR THE HP3000 SERIES 900 BASED ON THE DTC ..picturea:\int12.GAL,65535,49151,2,78,23, While the DTC is the best solution to connect end-users to HP and non- HP systems, there is a need to give end-users not attached to the DTC access to HP3000 Series 900 applications. This is done using the Telnet/TCP/IP protocol. To provide this multivendor connectivity without trading off performance, a dedicated processor card was developed to offload the HP3000 CPU. This card converts Telnet into the optimized protocol AFCP. These solutions are optimized for applications designed with Vplus block -mode, but also support character-oriented applications. Depending on the number of sessions required, two solutions exist: 1. HP ARPA Telnet Access card: this is a card that resides in the DTC48 and provides a maximum of 40 opened Telnet/XL sessions to one or more HP3000s. 2. HP ARPA Telnet Express: this is a hardware server that is connected directly to the LAN and provides a maximum of 80 opened sessions to one or more HP3000s. .PA III.4 ENHANCED CONNECTIVITY WITH THE DTC, END 1991 ..picturea:\int11.GAL,65535,49151,2,78,23, HP's DTC now provides consistent access to HP and non-HP systems, this in simple or complex network configurations. End-users can now forget about networks configurations and focus on their application requirements. By using standards, Network managers can minimize the number of protocols on their backbone, making it easier to manage and reducing operating cost as we will see later on. The future step to come in terms of end-user connectivity will contribute to enhance this consistent, location-independent access to systems for DTC and non-DTC end-users such as PC & other workstations: 1) The "back-to-back" capability will now be supported in both local LAN or extended LANs environments, this allowing for instance classic HP3000 remote access for both local & remote end-users. 2) Any DTC port can be accessed by any Telnet source. It will allow PCs, workstations to access a pool of ports connected to a system, or an X.25 PAD for outgoing purposes, in total transparency. This is accomplished without having to be aware whether the target system is connected directly to a LAN, or not. Application transparency will thus be improved by this enhanced connectivity based on HP's DTC: - Integration of existing non-ARPA systems in extended LANs configurations in addition to local configurations. - Integration of Telnet workstations (PCs, etc..) which benefit from DTC switching power. This will be possible with HP OpenView DTC Manager release 12.0, available in December 1991. III.5 DTC FEATURES SHORT DESCRIPTION ..picturea:\int20.GAL,65535,49151,2,78,23, The benefits of the new DTC capabilities come not only from added connectivity, but also from the following new features: 1. A full standard implementation insures greater connectivity with systems in simple or complex network environments (With bridges, and IP routers). 2. End-user productivity and ease-of-use is increased by new features such as multi-session, use of network symbolic names or application mnemonic names. These features also contributes to increase application transparency. 3. You can avoid duplication of expensive resources by sharing them between multiple HP systems. For example, one printer can be shared transparently by multiple HP3000 (MPE/XL, MPE-V) and HP9000 systems. 4. The DTC is provided with a certified interoperability stamp. This stamp is a consequence of the extensive in-house tests done with different non-HP systems. 5. New tools will help to improve HP9000 incoming network access security, by giving capabilities to check a caller's source addresse. Additionaly powerfail recovery will soon be supported for switched-port accessing HP3000 Series 900 systems. 6. The protocol timers & specific inter-network routes can be pre- configured, in order to optimize the performance and network resources availability. There is no need to "tune" each individual parameter, there is simply a selection of network "profiles" that can be complted during configuration. The performance enhancements in DTC Release 10.5 results in a DTC capacity gain of 20-50% for medium to heavy Telnet data entry workloads. This extra power can be used to support more active users or printers. Release 10.5 enhancements also reduce the S800 CPU utilization per active DTC Telnet user as much as 20% for medium to heavy usage. Thus you have additional host power to handle more users or heavier tasks. An important point to note is that measurements taken versus 3rd party Telnet servers indicate that the S800 host CPU utilization per DTC session is as much as 20% lower than the competition. That makes the DTC the best choice for conserving your host CPU cycles when your data entry loads are significant. The DTC will support MPE-iX Open Systems efforts with a richer higher performance Ti/o interface, this to provide for instance better performance for DBMS applications such as Oracle/Ingres. This enhancement effort has been conducted in cooperation with DBMS vendors and positions the DTC as an ideal terminal server for 4GL & DBMS environments. Use of these enhancements require the release 3.1 or a general patch for 3.0 of MPE/iX operating system. .PA III.6 HP OPENVIEW NETWORK MANAGEMENT APPLICATION INTEGRATION ..picturea:\int15.GAL,65535,49151,1,79,24, In multiple systems environments, the DTC is configured, downloaded from and managed by a PC-based OpenView Windows workstation running HP OpenView DTC Manager software. This software provides the following device management functions: o Configuration Management o Fault management ( identify/diagnose and resolve problems quickly ) for both DTC and Telnet devices o Performance Management o Security Management o Download and Upload functions of the DTC software The benefits of network management integrated under HP OpenView are the following: 1) Seamless integration of HP DTCs, Switches, PADs, Hubs, Routers and System management under HP OpenView ; Based on the HP OpenView multiple applications integration, a single-source can manage network components, facilitating support and reducing costs and overhead. The HP OpenView Management workstation is therefore not a resource dedicated to the DTC, but rather a tool to increase network efficiency and minimize problems resolution & network downtime. 2) The DTC network management feature set allows you to control the cost of operation by optimizing training (when management is centralized and based on a single tool) and centraling network monitoring control from a single point in the network. Obviously these features are not required in all customer environments. In standalone environments where the requirement is to manage the terminal servers from the system itself, it is easily accomplished via HP's Host-based management functionality. .PA III.7 Competitive features in host based management ..picturea:\hbfunc.gal,65535,49151,2,79,27, In the case ofstandalone sites, typically the requirement is to manage devices easily, as if they were part of the system. From an MPE XL standpoint This is how the DTC has been managed since the MPE XL introduction; It behaves as a LAN MUX. With General release 3.1 of MPE-XL, HP enhanced its host based management functionality to offer a full solution for local and remote access to MPE XL systems. From an HP-UX standpoint In Q1 91, HP introduced DTC host-based management capabilities to support both DTC48 & DTC16 platforms. This is an entry level product compliant with the OpenView strategy. .PA III.8 COMPETITIVE COMPANY-WIDE NETWORK MANAGEMENT ..picturea:\int41.GAL,65535,49151,2,78,23, The next HP OpenView release 12.0 will bring the capability to use the data "main stream" as a way to communicate between management stations. In the above example, the central station manages local devices, but also: (1) Remote DTCs host-based managed by one HP3000 Series 900 or HP9000 Series 800. (2) Remote DTCs using the DTC/X25 XL link managed by a DOS workstation (3) Remote DTCs connected on extended LANs managed by a DOS workstation (Note that extended LANs are LANs interconnected with bridges or routers) When customers have remote sites, whether all PC-based managed or a mix of host-based and PC-based managed environments, there is a way to centrally manage all DTCs. Even if a management station is required per site (for downloading the DTCs), one master network operator can manage all his terminal servers from his location. It avoids loss of time to call remote operators and simplifies procedure of receiving remote information (release #, specific parameter, etc..). When one of the sites is host-based managed, the central operator can also manage the end-users; Thus avoiding the need to have specific DTC management in small environments. When this site grows, and evolves to a PC-based network management solution, the mechanism of central management limits the effort by providing already existing information to the new management station. Whatever the network configuration is, there is a way to centrally manage DTCs. III.9 Steps in the HP3000 Terminal connect life ..picturea:\dtc3life.gal,65535,49151,2,79,27, Looking at the first and second rows, and then at the third and fourth rows we can now describe the different sets of functionality and hardware that have been and will continue to be enhanced. Both hardware and functionality are actually linked to the type of management which is being used. Looking now at the top two rows: The DTC providing multivendor connectivity will be enhanced to provide: o Open System Support /iX Performance with the a new "Field- mode" optimized for Oracle & Ingres DBMS environments. o Application Transparency Improvements with new features such as DTC Back-to-Back over IP routers & Telnet to port. o Selectable PADSup profiles, thus improving the X25 access transparency and performance. o Better security with enhanced powerfail recovery. o High availability with autorestart of X.25 and Telnet Access cards Looking now at the bottom two rows: From a Host based management standpoint HP continues to make enhancements. One example is this full solution for local and remote access to MPE XL systems (by managing also the X.25 access) available with MPE-XL release 3.1. The new Open System Support /iX improvements will also be available with host-based management. .PA III.9 Steps in the HP9000 Series 800 Terminal connect life ..picturea:\dtc9life.gal,65535,49151,2,79,27, In PC-based network management environments, the following two steps will provide the following new capabilities: o First , the DTC will provide better security for HP9000 access, this enabling applications to better control use of LANs. This will be done via 1- the capability for the HP9000 system to identify DTC incoming call and 2- an application-transparent solution for DTC devices access. o Second , the DTC will be able to contribute to HP-UX High- end OLTP performance, while providing high-level DTC-MUX Application Transparency. Additionaly, new features to come with future releases will serve to minimize the differences between DTC and MUX ports. It's HP 's aim to provide application access to DTC devices, identification of incoming DTC connected end-users, and the ability to deliver security & device required in networked environments. One other focus will be on the performance aspect, with the objective to decrease the system overhead due to protocol processing on the HP9000 system. .PA III.10 HP'S MULTIVENDOR ADVANTAGE ..picturea:\int14.GAL,65535,49151,2,78,23, It is one objective of the DTC to provide high-level functionalities, but also to provide functionalities that you can use in any specific network and application environment. The DTC is a solution and not just a tool. 1) HP is the only vendor to support a complete and full "end-to-end" - From Terminal to application-multivendor communication solution for both local and remote end-users. For example a single DTC-connected HP terminal accessing both Block mode HP3000 and DEC full screen applications is the kind of service HP wants to provide and support. 2) The DTC differentiates itself from the competition by insuring multivendor interoperability through extensive in-house testing. The DTC has been tested and qualified in complex network environments which include many non-HP systems and equipment. It has been optimized for both HP-only systems and multivendor installations. 3) In addition, and in order to certify the use of the DTC in non-HP configurations ( Which have not been already been tested in-house ), HP offers a "Multivendor test guide", product & service to be used as a validation test. This validation test will check the end-to-end communication path, from the terminal to the application , for any network specific configuration. All HP support services benefit from extensive "real life" studies based on customer configurations. When combined with existing HP NETASSURE product offering, these support services will give you the best possible insurance that your specific configuration will provide you with lasting and uninterrupted service. .PA III.11 HP results in the Terminal Server Market ..picturea:\mktshare.GAL,65392,49151,2,77,23, This chart is one of the results of the important outbound communication done at the DTC release 10.5 introduction. It demonstrates that HP is recognized now as one of the Leading Terminal server Manufacturers. This result 7.8% of the market share is today mainly due to the results of the DTC for HP3000 connectivity. One of our goals is to increase this share by demonstrating that HP's DTC is the best solution for HP9000 systems connectivity in networked environments. 3 main strengths can help us to achieve this goal: o Providing fast access to HP9000 with minimum system overhead o Providing application transparency between DTC & MUX ports o Providing added features to a classic terminal server solution such as better end-user friendliness, network transparency, or connectivity- default recovery mechanism. ..in order to provide superior solutions at slight price premium. .PA III.12 FOR MORE INFORMATION The "TIOPROD" network hotline contains more specific information about features, requirements, supported devices & systems, network management , as well as a complete competitive analysis . Please refer to this hotline if you need more details. .pa IV. A year in the MUX life for HP 9000 customers As defined in the strategic direction, HP continues to invest to increase competitiveness and price/performance of our MUXs for multi- user systems and workstations. ..picturea:\muxlife.gal,65535,49151,1,78,27, HP9000 multi-user systems HP-PB (NIO) systems (808, 815, Series 8x2, Series 8x7) In September 89, HP introduced a very competitive 8 port MUX designed for the new HP-UX systems based on the NIO technology. This MUX perfectly fits the requirements of performance, and modularity for low port counts. Through 1990, HP introduced several enhancements to the 8 port NIO MUX: o Boot capability for Series 8x2 systems o A new Asynchronous distribution panel that provides the 8-port MUX with RS 422C capabilities. This offers the capability of running long distance connections, as well as providing a way to connect DEC- types of terminals such as HP's 700/32. o With the HP-UX 8.0 release, HP included the support of the Access Port functionality. This provides console capabilities from a remote site, therefore enhancing supportability and facilitating management of remote systems. With the introduction of the Series 8x7 systems (August 91) The next step forward in the terminal connect offering was the introduction of the new family of 16-port multiplexers that brings the following major enhancements: o More ports per I/O slot of the HP9000 systems, o A major price/port reduction (30%) compared to the 8-port MUX, o The support of the RS-423 standard interface (compatible with RS-422 and RS-423 equipments) to allow long distance cabling and support of DEC-types terminals such as HP's 700/32 and 700/60, o The support of line speed up to 38.4 kb/s, o The support of hardware flow-control on RS-232 modem lines. This enhances the support of binary stream and of peripherals that cannot use the software (Xon/Xoff) flow- control,. o More flexibility in the connector choice (DB-25, RJ-11, RJ45, ...) and distribution panels. This provides with the capability to use a customized cabling scheme involving equipments such as Dataswitches, patch panels, wiring cabinets, ... In addition to these new add-on multiplexers, HP introduced with the Series 8x7 systems the "personality cards" or "integrated I/O card". This system component that is always bundled in the base configuration integrates on a single card several functionalities such as: o RS-232 asynchronous ports with the support of the local and remote console with Access Port functionality, o SCSI interface, o Centronics interface. By the end of 1991, The personality card will be further enhanced to support more ports in the same I/O space. CIO systems (825,835,85x) These systems have had a tremendous growth in the business application area, therefore requiring a higher number of users to be connected to the SPU. In June 90, HP introduced a new 16 port MUX. It allows HP to be more competitive for high end configurations as it takes the same I/O space as the current CIO6 port MUX while giving nearly 3 times more connections at a nearly 20% lower price per port. In addition the CIO 16 port MUX supports long distance connections by offering an RS 422C option. .PA HP9000/300,400 workstations HP is facing increased competition for price performance in the workstation market. While the connectivity requirements are low in terms of ports, the DIO 4 port MUX sometimes was insufficient, therefore requiring an expensive extension chassis to be purchased. It was also providing a single modem port. In April 90, HP increased the price/performance competitiveness of workstations requiring to control up to 8 lines. HP introduced a new powerful DIO 8 port MUX (for DIO II backplane systems) which doubles the current asynchronous line potential, and offers full modem control on all ports. At the same time HP introduced a new interface option which provides RS422C connections. HP9000/400,700 workstations For the EISA based workstations, (400 / 700) which do not intend to address the multiuser market, the need for a MUX is lower than for the previous Series 300. In addition, many suppliers for a standard based MUX can be found in the market place. Therefore, the workstation group intends to list or reference a 3rd party solution for an ISA/EISA asynchronous MUX for the HP9000 Series 400/700 workstations. Contact the workstation sales center for latest details. .PA V. A year in the life of HP PADs ..picturea:\2335life.gal,65535,49151,1,78,27, In May 90, HP enhanced the 2335A PAD by implementing the X.25 and X.3 CCITT-84 recommendations on the platform providing features such as Network User Identification, Call Redirection or Extended Called Address. At that time, the overall performance was improved with the support of 64Kbps speed on the synchronous RS-232 link, allowing higher throughput. Since that time, 2335As can be used in either X.25 PAD or Stat MUX configurations with HP9000 and VAX computers. Access to a remote site for local DTC users was made available by supporting extended switching to the 2335A, providing them with a "PAD pool" for outbound access. Since the 1st half of 91, HP provides the OpenView Switch/PAD Manager product, thereby offering a centralized network management solution for 2335As and M45s. This network management tool runs concurrently with the OpenView DTC manager on the same OpenView PC. Remote HP 9000 printers are supported when connected to a 2335A in X.25 PAD configuration. .pa VI. Conclusion ..picturea:\conclus.gal,65381,49113,2,73,25, HP has a very clear strategy in terms of end-user connectivity. The building blocks are in place to have a very competitive offering with consistent location-independent access, benefits of standard and multivendor protocols, scalable network management. 1992 is a key year to even further help you and your customers be successful in business. 1. Needs for standalone systems are covered with a very complete and competitive family of MUXs, Pads and terminal servers. 2. HP has "best-in-class" end-user connectivity solutions to allow your customer to consistently access their HP or Non HP computers whether they are local or remote, combining the benefits of standard and proprietary protocols. 3. Customers can have the assurance that the products and features are manageable in a cost effective manner as best fit their needs. This is achieved with entry level and fully integrated multivendor and multi- system device management solutions. HP is clearly your customer's best choice for end-user connectivity.